Json summary meta data #52
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At the moment we have a JSON file for each of the flow config objects, alongside the HTML reports. The results summary page which ties them all together is HTML only. There is no way of getting the information programmatically, without doing something like parsing the HTML... which is error prone and messy. The ResultsSummary is a Pydantic model which can then be dumped to JSON. Signed-off-by: James McCorrie <[email protected]>
machshev
force-pushed
the
json_summary_meta_data
branch
from
6d8dc92 to
b738b5a
Compare
Signed-off-by: James McCorrie <[email protected]>
hcallahan-lowrisc
approved these changes
Nov 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment we have a JSON file for each of the flow config objects, alongside the HTML reports. The results summary page which ties them all together is HTML only. There is no way of getting the information programmatically, without doing something like parsing the HTML... which is error prone and messy.
The
ResultsSummaryis a Pydantic model which can then be dumped to JSON, and this is used to provide the missing results summary JSON that corresponds with the individual flow config results JSON files.Fixes: #51